Skip to content

Automate creating a PR for version bump#1366

Merged
zetter-rpf merged 1 commit into
mainfrom
automate-release-bump-pr
Mar 9, 2026
Merged

Automate creating a PR for version bump#1366
zetter-rpf merged 1 commit into
mainfrom
automate-release-bump-pr

Conversation

@zetter-rpf

Copy link
Copy Markdown
Contributor

Related to #1362

I wasn't able to make a PR that merged in the changes because of our branch protection rules.

There are ways to bypass them but I think we'd have to create a specific app in order for us to target the bypass.

Instead I thought an easier first step would be to automate creating a PR instead

@zetter-rpf zetter-rpf marked this pull request as ready for review March 6, 2026 11:00
Copilot AI review requested due to automatic review settings March 6, 2026 11:00
@zetter-rpf zetter-rpf temporarily deployed to previews/1366/merge March 6, 2026 11:00 — with GitHub Actions Inactive

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the manual bump-version GitHub Actions workflow to avoid direct pushes to protected branches by pushing the version bump to a new branch and automatically opening a pull request to main.

Changes:

  • Grants pull-requests: write permission to the workflow token.
  • Captures the bumped version as a step output and uses it to name the branch/commit/PR.
  • Pushes the bump commit to a new branch and creates a PR via gh pr create.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread .github/workflows/bump-version.yml Outdated
Comment thread .github/workflows/bump-version.yml
Comment thread .github/workflows/bump-version.yml
Comment thread .github/workflows/bump-version.yml
I wasn't able to make a PR that merged in the changes because of our branch protection rules.

There are ways to bypass them but I think we'd have to create a specific app in order for us to target the bypass.

Instead I thought an easier first step would be to automate creating a PR instead

@adrian-rpf adrian-rpf left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGMT

@zetter-rpf zetter-rpf merged commit f27a359 into main Mar 9, 2026
7 of 8 checks passed
@zetter-rpf zetter-rpf deleted the automate-release-bump-pr branch March 9, 2026 17:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants